Sourced from @​sentry/node's releases.

8.28.0

Important Changes

• Beta release of official NestJS SDK

This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

• fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)

This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were smaller than the actually measured values. We apologize for the inconvenience!

Other Changes

• feat(nestjs): Add SentryGlobalGraphQLFilter (#13545)
• feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#13264)
• feat(nextjs): Add bundleSizeOptimizations to build options (#13323)
• feat(nextjs): Stabilize captureRequestError (#13550)
• feat(nuxt): Wrap config in nuxt context (#13457)
• feat(profiling): Expose profiler as top level primitive (#13512)
• feat(replay): Add layout shift to CLS replay data (#13386)
• feat(replay): Upgrade rrweb packages to 2.26.0 (#13483)
• fix(cdn): Do not mangle _metadata (#13426)
• fix(cdn): Fix SDK source for CDN bundles (#13475)
• fix(nestjs): Check arguments before instrumenting with @Injectable (#13544)
• fix(nestjs): Ensure exception and host are correctly passed on when using @​WithSentry (#13564)
• fix(node): Suppress tracing for transport request execution rather than transport creation (#13491)
• fix(replay): Consider more things as DOM mutations for dead clicks (#13518)
• fix(vue): Correctly obtain component name (#13484)

Work in this release was contributed by @​leopoldkristjansson, @​mhuggins and @​filips123. Thank you for your contributions!

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

... (truncated)

Sourced from @​sentry/node's changelog.

8.28.0

Important Changes

• Beta release of official NestJS SDK

This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

• fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)

This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were smaller than the actually measured values. We apologize for the inconvenience!

Other Changes

• feat(nestjs): Add SentryGlobalGraphQLFilter (#13545)
• feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#13264)
• feat(nextjs): Add bundleSizeOptimizations to build options (#13323)
• feat(nextjs): Stabilize captureRequestError (#13550)
• feat(nuxt): Wrap config in nuxt context (#13457)
• feat(profiling): Expose profiler as top level primitive (#13512)
• feat(replay): Add layout shift to CLS replay data (#13386)
• feat(replay): Upgrade rrweb packages to 2.26.0 (#13483)
• fix(cdn): Do not mangle _metadata (#13426)
• fix(cdn): Fix SDK source for CDN bundles (#13475)
• fix(nestjs): Check arguments before instrumenting with @Injectable (#13544)
• fix(nestjs): Ensure exception and host are correctly passed on when using @​WithSentry (#13564)
• fix(node): Suppress tracing for transport request execution rather than transport creation (#13491)
• fix(replay): Consider more things as DOM mutations for dead clicks (#13518)
• fix(vue): Correctly obtain component name (#13484)

Work in this release was contributed by @​leopoldkristjansson, @​mhuggins and @​filips123. Thank you for your contributions!

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for

... (truncated)

• e78f15e release: 8.28.0
• f834625 Merge pull request #13560 from getsentry/prepare-release/8.28.0
• c2258fb meta: Update CHANGELOG for 8.28.0
• 9e585e7 Merge branch 'develop' into prepare-release/8.28.0
• 9b8f9ea fix(nestjs): Ensure exception and host are correctly passed on when using @​Wi...
• e8ed7c2 Merge remote-tracking branch 'origin/master' into prepare-release/8.28.0
• 5605401 meta: Update CHANGELOG for 8.28.0
• c9c346c ref: Add external contributor to CHANGELOG.md (#13552)
• a8ff09f chore(nestjs): Add note about SentryGlobalGraphQLFilter in nestjs README (#...
• 83864fa chore(nestjs): Promote NestJS SDK to beta state (Readme) (#13521)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)